iLoADER

HOME

Common Issues

Unicode Support

- ILoader v2.5 scripts are unicode compliant. This means that the script looks strange in notepad (all the data is on one line). To edit 2.5 scripts, use wordpad.

- If any changes are made to a script file via the iLoader editor the file containing the script will be converted so that it's encoding format is UNIcode.

- New (2.5) iLoader scripts are not backwards compatible with previous versions of iLoader due to unicode support. To create a backwards compatible script, open the script file in explorer (using notepad) and Save as, setting the Encoding option = ANSI.

- When loading UNIcode data the UNIcodeFLAT and UNIcodeDELIMETED options for FORMAT must be used within the TABLE_DECLARATION section.

Updating Data

- When updating, if a field specified in the TABLE_DEFINITION section doesn't exist in the Engine table that is being updated a new field is created and no warning is given. Care must therefore be taken to avoid typing mistakes.

- When updating, WIDTH in the TABLE_DECLARATION refers to the number of columns in the Engine table as opposed to the number of columns in the data file.

Re-running failed scripts

- If a script is created and run and it fails when loading the data (typically and Error Adding File message will be seen), it will have created an empty table/database structure. (This can be seen by starting up the AMC Repository Applet immediately after the script has failed). This can cause problems when making a change to the table definition and then re-running.

ILoaderWizard

- Use iLoaderWizard to generate basic scripts (on the LOAD DETAILS screen, choose Write Scripts) and then edit the scripts in iLoader.

Configuring iLoader

- Script paths are read from LoaderServer, not LoaderClient.

- When running client-server it is generally wise to use UNC paths

- Script paths are automatically converted to UNC paths so long as the script directory is shared or in a sub-folder of a shared directory.

- Existing script files are not overwritten when clicking on the "Create Default Files" option. The new project simply points to the existing files.

Configuration Errors

Error Cause Solution
Password is not entered correctly. ILoader displays "Cannot Start Engine" Cerlog contains "Illegal Password For User SYSTEM". Enter the SYSTEM password correctly (note that passwords in iLoader are case sensitive) The password will need to be entered the first time that iLoader is run.

Script Errors

Error Cause Solution
  Files are defined as FLAT when they are DELIMITED  
  WIDTH is incorrectly defined in the TABLE_DECLARATION when updating. WIDTH refers to the number of columns in the Engine table as opposed to the number of columns in the data file.
  The wrong combination of scripts within a script set is often run when people don't change the DO_…….SCRIPT = TRUE to FALSE or vice versa.  

Problems with data

Symptoms Possible Cause Solution
Records get shorter Data is in wrong fields Wrong number of records loaded. Row Delimiters in the middle of a record. Use qualifiers if there is a risk of a row delimiter being contained within a record.

Error Messages

Error Message Possible Cause Solution
Error Adding File - cerlog contains "Specified file is in OTF-16 format" The data file is in UNIcode format, possibly because it was opened or viewed in iLoader 2.5 Open the data file and re-save with ENCODING set to ANSI (assuming the file is not supposed to be UNIcode)
Error Adding File FORMAT is specified as DELIMTED but no DELIMITER keyword is provided. If the file is supposed to be DELIMTED, add the DELIMITER keyword, otherwise change the FORMAT to be FLAT.
Error Adding File The file has been declared as delimited, but has been defined as flat In TABLE_DEFINITION Check that correct OFFSET or ORDINAL is used.: If loading DELIMITED files, the ORDINAL value is 0 based, increasing by 1 for each field. For FLAT files, check that the OFFSET starts at 0 and that subsequent values match the field widths as specified.
Cannot Start Engine. Engine. Cerlog contains "Illegal Password For User SYSTEM" Password is not entered correctly. Passwords in iLoader are case sensitive. The password will need to be entered the first time that iLoader is used.

Known Issues

- When you click the Generate button in the Importers wizard, if you get a 'Save Changes' message, you must select 'NO' or all changes will be lost.

  Online & Instructor-Led Courses | Training Videos | Webinar Recordings
© Alterian. All Rights Reserved. | Privacy Policy | Legal Notice